Re: [GENERAL] equivalent of sqlload?
От | Herouth Maoz |
---|---|
Тема | Re: [GENERAL] equivalent of sqlload? |
Дата | |
Msg-id | l03110702b286cd256570@[147.233.159.109] обсуждение исходный текст |
Ответ на | Re: [GENERAL] equivalent of sqlload? ("Michael A. Koerber" <mak@ll.mit.edu>) |
Ответы |
Re: [GENERAL] equivalent of sqlload?
|
Список | pgsql-general |
At 21:01 +0200 on 25/11/98, Michael A. Koerber wrote: > > Now...I have broken the "copy" process down into smaller chunks and make > multiple calls to "copy". I have a total of about 5.4 million records and > the job isn't done yet...my Pentium 433 has been working on this copy for > over 24 hours. Try putting all the separate COPYs in one transaction. BEGIN TRANSACTION; COPY... COPY... COPY... END; Without the surrounding transaction, each copy is a transaction and requires transaction overhead. I don't know how much time this will save, though. Are you sure you dropped all the indices? When you declare a primary key it declares a unique index, so watch out for that as well. Herouth -- Herouth Maoz, Internet developer. Open University of Israel - Telem project http://telem.openu.ac.il/~herutma
В списке pgsql-general по дате отправления: